System and method for dynamic generation of a single user interface for display and entry of medical imaging configuration data

ABSTRACT

A system and method for dynamically generating an interface includes a hierarchical organization data file defining a hierarchical organization of subsystems of a medical imaging scanner and at least one parsing component to extract configuration parameter names from the data file and generate a graphical representation of the hierarchical organization of the medical imaging scanner. A configuration servlet extracts configuration parameters of the medical imaging scanner, associates the configuration parameters with the graphical representation of the hierarchical organization, and displays the configuration parameters and graphical representation of the organization in a single user interface such that the configuration parameters can be reviewed and edited in the single user interface.

BACKGROUND OF INVENTION

The present invention relates generally to medical imaging systems, andmore particularly, to a system for dynamic generation of a singleinterface for a medical imaging scanner to allow a user to review andedit configuration parameters of the medical imaging scanner from thesingle web-based interface.

Medical imaging scanning devices, such as computer. tomography (CT)systems, x-ray systems, magnetic resonance imaging (MRI) systems,positron emission tomography (PET) systems and the like, are defined bya number of subsystems that control the major functionalities of thedevice. For example, some subsystems of an x-ray scanner include anx-ray generator, a table positioner, a system control, and an operatorconsole. These subsystems may be further subdivided into subsystems ofthe subsystem, or micro-subsystems. For example, the operator consolemay include multiple control interfaces such as keyboards, mice, andtouch-screen monitors wherein each has multiple outputs or inputs ormultiple functions and therefore is considered an individual subsystemof the operator console subsystem and has specific software dedicated tointerpreting user input therefrom. This amalgamation of subsystemsresults in a distributed overall system hardware configuration. Due tothis distributed configuration, the overall x-ray scanner functionalityis commonly achieved using distributed object oriented infrastructurecomponents as a middleware interface between the specific softwarerunning the various scanner subsystems or between the subsystems andexternal user applications.

One type middleware implementation that is commonly selected in medicalimaging scanners is Common Object Request Broker Architecture (CORBA®).CORBA® is a registered trademark of Object Management Group, Inc., ofFarmingham, Massachusetts. A CORBA® architecture is aplatform-independent architecture that facilitates the interaction ofcomputer applications that are not readily capable of interaction. Aprogram based on the CORBA® architecture will be able to communicatewith other applications regardless of computer manufacturer, operatingsystem, programming language, and network. CORBA® applications arecomposed of “objects” or individual units of software that can becombined to develop functionality. An “object” is generally defined as aprogramming component that can be used to build arrangements ofvariables and operations therein. Applications built with this“object-oriented” programming are developed in a block-by-block or“object-by-object” fashion. These arrangements can be logically groupedinto “structures” or “classes.” Each “class” can be designed to performa specific operation or operations on data passed to it by anotherclass.

Typically, in object-oriented programming, each object includes an“interface.” The “interface” for each object is the syntax of the objectthat allows other objects to invoke the object. A first object thatwishes to invoke an operation by a second object uses the interface to“call” the second object, and pass on the arguments on which theoperation must be performed. When the operation is complete, theinterface is then used to collect the results for forwarding to thedesired destination; typically, back to the first object that requestedthe operation.

The distributed object oriented infrastructure components provide ameans whereby the interface definition is independent of programminglanguage. Independence is achieved by mapping the interface to multipleprogramming languages such as C, C++, and Java®. Java® is a registeredtrademark of Sun Microsystems, Inc., of Palo Alto, Calif. Thisseparation of the interface and the execution is a chief benefit ofimplementing distributed object oriented infrastructure components. In amedical imaging device, distributed object oriented infrastructurecomponents are used to enable the interaction of the various subsystemsof the medical imaging device. As such, the distributed object orientedinfrastructure components need to access configuration data necessaryfor the proper running of the subsystem. This configuration data isstored in configuration files which are initially defined and usedduring the running of the system. During the servicing of such an x-raysystem, a service engineer uses an interface to access the configurationdata. Should the engineer or other service technician need to change orotherwise update the configuration data, the engineer must use a secondand separate application that provides a second and separate userinterface specifically designed to facilitate editing of theconfiguration data. That is, a second user interface is required for theuser to change the configuration parameters and communicate thosechanges to a distributed object oriented infrastructure component forimplementation.

For example, a service engineer, when servicing a scanner, must firstreview the data in one user interface and then switch to a separate userinterface to edit the data. This requirement of a second and separateuser interface to permit the service engineer to change configurationdata creates a servicing and/or maintenance process that is arduous,time consuming, and error prone.

The process of changing the configuration data can be arduous becausethe service must switch repeatedly between the “viewing” interface andthe “editing” interface. Furthermore, by requiring a separate userinterface for editing configuration data, the service engineer iseffectively tethered to the system. That is, while the “viewing”interface is typically displayable in a web browser and therefore, caneasily be made accessible remotely, the “editing” interface is not asreadily accessible from remote locations. That is, while the “viewing”web browser interface is readily compliant with internet compatibilitystandards, the “editing” interface is not necessarily compliant withthose standards. Therefore, the service engineer is effectively tetheredby the “editing” interface to a local proximity of the medical imagingdevice being serviced.

Additionally, the process of changing the configuration data issusceptible to error because the imposition of a second and separateinterface for editing configuration parameters raises the probability ofhuman error. For example, the service engineer is more likely to entererroneous configurations or enter the correct configuration in anincorrect area when switching from the review interface to the separateedit interface. Errors in configuration data can cause the medicalimaging device being serviced to operate improperly or not at all. Insuch a case, a second servicing is typically required to remedy theconfiguration error. These repetitive service calls can be extremelycostly in both time and resources. In addition, the servicing downtimefor the medical imaging scanner can be an impediment to the efficientand effective practice of medicine.

It would therefore be desirable to have a system and method capable ofdynamically generating a single user interface for display and entry ofmedical imaging configuration parameters.

BRIEF DESCRIPTION OF INVENTION

The present invention provides a system and method of dynamicallygenerating a single user interface for the display and entry of medicalimaging configuration parameters that overcomes the aforementioneddrawbacks. Specifically, the invention is directed to a system to gatherthe necessary configuration parameters from various subsystems of amedical imaging system and dynamically generate a single web-based userinterface that displays the configuration parameters and allows theparameters to be edited.

In accordance with one aspect of the invention, a system of dynamicallygenerating an interface is disclosed that has a hierarchicalorganizational data file defining a hierarchical organization ofsubsystems of a medical imaging device and at least one parsingcomponent to extract configuration parameter names from the data fileand generate a graphical representation of the hierarchical organizationof the medical imaging device. A configuration servlet is provided toextract configuration parameters of the medical imaging device,associate the configuration parameters with the graphical representationof the hierarchical organization, and display the configurationparameters and graphical representation of the organization in a singleuser interface wherein the configuration parameters can be reviewed andedited in the single user interface.

In accordance with another aspect of the invention, a method ofdynamically generating an interface is disclosed that includes defininga hierarchical organization of subsystems of a medical imaging device ina hierarchical organization data file, extracting configurationparameter names from the data file, and extracting configurationparameters of the medical imaging device. The method further includesgenerating a graphical representation of the hierarchical organizationof the medical imaging device, associating the configuration parameterswith the graphical representation of the hierarchical organization, anddisplaying the configuration parameters and the graphical representationof the hierarchical organization in a single user interface. In thisregard, the configuration parameters can be reviewed and edited in thesingle user interface.

In accordance with yet another aspect of the invention, a medicalimaging scanner is disclosed that includes a plurality of subsystems aswell as a computer programmed to define a hierarchical organization ofsubsystems of a medical imaging device in a hierarchical organizationdata file wherein sections map to subsystems of the medical imagingscanner and subsections map to sub-subsections of the medical imagingscanner. The computer is also programmed to extract configurationparameter names from the data file, extract configuration parameters ofthe medical imaging device, and generate a graphical representation ofthe hierarchical organization of the medical imaging device. Thecomputer then associates the configuration parameters with the graphicalrepresentation of the hierarchical organization and displays theconfiguration parameters and the graphical representation of thehierarchical organization in a single user interface thereby allowingthe configuration parameters to be reviewed and edited in the singleuser interface.

Various other features, objects and advantages of the present inventionwill be made apparent from the following detailed description and thedrawings.

BRIEF DESCRIPTION OF DRAWINGS

The drawings illustrate one preferred embodiment presently contemplatedfor carrying out the invention.

In the drawings:

FIG. 1 is a block schematic diagram of a medical imaging system inaccordance with one embodiment of the present invention.

FIG. 2 is a graphic representation of software components used todynamically create a user interface in accordance with one embodiment ofthe present invention.

FIG. 3 is a graphic representation of an implementation of access rightsmanagement in accordance with one embodiment of the present invention.

FIG. 4 is a representation of a graphical user interface in accordancewith one embodiment of the present invention.

FIG. 5 is a schematic representation of a multi-node network of medicalimaging systems.

DETAILED DESCRIPTION

The present invention is operable with a wide variety of medical imagingsystems and devices. As will be described in detail below, the presentinvention is not hardware specific and, therefore, readily portable andadaptable for operation with various medical imaging systems. As will befurther described, the claimed invention is operable with middlewareinterfaces regardless of the specific hardware or software of theunderlying system. Specifically, the current invention is operable witha wide range of medical imaging systems that can be defined bysubsystems and subsystems within the subsystems, or micro-subsystems,that readily map to middleware interfaces. However, a single systemcomponent can make or be a subsystem, as that term is used herein. Suchsystems are defined to include any imaging system, including computertomography (CT) systems, x-ray systems, magnetic resonance imaging (MRI)systems, ultrasound systems, positron emission tomography (PET) systems,and the like.

FIG. 1 is a graphical representation of examples of various subsystemsof a medical imaging scanner. An x-ray scanner 100 is shown, includingan x-ray generator subsystem 102, a table positioner subsystem 104, asystem control subsystem 106, a subsystem coolant system 107, and anoperator console subsystem 108. Though only specific subsystems areshown, it should be understood that the current invention contemplatesany number of subsystems. Furthermore, these subsystems may be definedby further subsystems or micro-systems. For example, the operatorconsole 108 may have multiple control interfaces such as a keyboard,mouse, buttons, touch screen monitor, switches, and dials. Each controlinterface is a further subsystem or micro-system of the operator consolesubsystem 108. This amalgamation of subsystems results in a distributedoverall system hardware and software configuration. Due to thisdistributed configuration, medical imaging scanner functionality iscommonly achieved using distributed object oriented infrastructurecomponents as a middleware interface between the specific softwarerunning on the various scanner subsystems or between the subsystems andexternal user applications.

The service computer 110, capable of generating a user interface,communicates with the x-ray scanner 100. Through a process that will bedescribed in detail below, the information necessary to generate theuser interface on the service computer 110 is gathered from thesubsystems 102, 104, 106, 107, 108 of the x-ray scanner 100.Corresponding to each subsystem 102, 104, 106, 107, 108 is at least onedistributed object computing infrastructure component 118. In apreferred embodiment, the distributed object computing infrastructurecomponent 118 is a CORBA® component. The component 118, when contactedby the service computer 110, extracts the desired configurationparameters from data files 120 and passes the configuration parametersto the service computer 110.

Therefore, FIG. 1 shows several subsystems from which the necessaryinformation to generate a user interface is gathered. As will be shown,the configuration parameters are organized in a user interface intosections and subsections such that subsystems of the medical imagingscanner are displayed as sections of the user interface and furthersubsystems of the subsystem, or micro-subsystems, are displayed assubsections.

Referring now to FIG. 2, examples of components used to extract andgenerate the user interface are shown. When a user initiates thegeneration of the user interface via browser 140, a configurationservlet 142 passes a configuration parameter name that will be displayedto configuration map class 144. The configuration map class 144 thenlocates a distributed object computing infrastructure component nameassociated with the requested configuration parameter name in aconfiguration map file 146 and returns the distributed object computinginfrastructure component name configuration servlet 142.

The configuration servlet 142 then passes the configuration parametername to an access-layout class 148. In response, the access-layout class148 retrieves layout information associated with the configurationparameter from an access-layout extensible markup language (XML) file150. After receipt of layout information the configuration servlet 142creates an organizational table for the later generated Hypertext MarkupLanguage (HTML) code. Then the configuration servlet 142 makes a call toa component service manager 152 to request the desired configurationparameter value.

The main parameters passed to the component service manager 152 includesection name, configuration parameter name, and the distributed objectcomputing infrastructure component name associated with theconfiguration parameter name. The service manager 152 retrieves therequested configuration parameters and, through the configurationservlet 142, sends a string representation value to a string parserclass 154, which extracts the actual data and stores it in privatevariables. The data is read from a “point-of-view” file which isorganized in a hierarchical manner that will correspond to thehierarchical manner of displaying the sections and subsections withinthe user interface. The string parser 154 then calls an HTML converterclass 156. In turn, the HTML converter class 156 converts the necessaryHTML and calls a control parser class 158. The control parser class 158extracts controls from a XML control file 160 and combines the data withHTML tags passed by the HTML converter class 156 to generate an HTMLoutput according to the hierarchical organization in sections andsubsections corresponding to the subsystems of the medical imagingsystem being accessed. Furthermore, the XML control file 160 sets forththe particular manner in which the configuration parameter will bedisplayed in the user interface. Specifically, the XML control file 160sets forth the manner in which each of data type of the configurationparameter. As such, different visual representations of the same dataare possible within the structure of the single user interface.

Upon receipt of the HTML output at the configuration servlet 142, theconfiguration servlet 142 places the HTML output in the correct row andcolumn of a table 161 generated by the configuration servlet 142. Thetable 161 is then passed to and displayed in a user interface within theuser's web browser 140 in the desired hierarchical organization and withthe desired number of rows and columns for the data. As such, the useris able to review the configuration parameters through the single userinterface.

After review of the configuration parameters, the user may conclude thatchanges to the configuration parameters are necessary. Upon submissionof a change to the configuration parameters, the currently displayedvalues, including the user changes, are passed to an HTML tag parserclass 162. The HTML tag parser class 162 parses the values into thespecific configuration parameters and passes them to the configurationservlet 142. The configuration servlet 142 then passes the changes to averification function 164 to verify the validity of the submittedchange. Numerous validation functions 164 are possible, each of which isnamed by the configuration servlet 142 at run time. The configurationservlet 142 uses the configuration parameter names to generate thevalidation function names. Thus, the number of validation functions 164defined is dependent upon the number of configuration parameters presentin the medical imaging scanner. After validation, the submitted changeis passed to the component service manager 152 to implement thesubmitted change. Therefore, through the single user interface, theservice engineer can review, edit and update any configurationparameters of the medical imaging scanner.

Included in the access-layout class 144 is support for access control ofvarious user profiles. Along with retrieving layout informationassociated with the configuration parameter from an access-layout XMLfile 150, the access-layout class retrieves access information. Theinformation is also stored in the map file 146. Specifically, the accessinformation is stored as an access rights string. Each value stored inthe map file 146 has a corresponding access rights string. As such, whenthe organizational table is generated by the configuration server 142, adetermination is made for each table entry as to whether the currentuser has access rights to change and/or view each entry. Furthermore,since each entry in the map file 146 has its own access rights stringassociated with it, each access rights determination is madeindependently.

Referring now to FIG. 3, a graphical representation of an example of anaccess rights string and corresponding profiles are shown. In the givenexample, “1”, “2”, “2”, and “1” represents the access rights string 166.The position in the access rights string 166 indicates the user profileunder consideration. The actual value of the digit indicates the type ofaccess allowed. Typically, a value of “1” indicates that the specificvalue associated with the access rights string is read-only for thegiven user profile and a value of “2” indicates that the value isread-write for the given profile. In such a case, a value of “3”indicates that the associated value is hidden from the view for thegiven profile. In this preferred embodiment, FIG. 3 shows that for: (1)User Profile 1: Doctors 168 have read-only access for the associatedvalue; (2) User Profile 2: Service Engineers 170 have read-write accessfor the associated value; (3) User Profile 3: Program Engineers 172 haveread-write access for the associated value; and (4) User Profile 4: anyOthers 174 that have access will have read-only access for theassociated value.

Referring now to FIG. 4, a graphical representation of a user interface176 is generated when accessing the medical imaging scanner forconfiguration review and editing. The interface 176 is shown displayedin a web browser 178 and complies with common internet protocolstandards so that it may be readily accessed either locally or remotely.The interface 176 is further broken down into a hierarchicalorganization section 180, which is a graphical representation of thesubsystems of the medical imaging scanner, and configuration parameterdisplay section 182, which displays the desired data. The hierarchicalorganization section 180 shows sections 184 and subsections 186 thatcorrespond to the subsystems of the medical imaging scanner.Additionally, hypertext transfer protocol (http) links 188 toinformation located externally from the medical imaging scanner, orexternal links 188, can be provided as an additional resource for theuser, which when selected causes the interface to seamlessly display theexternal information.

Upon selecting a subsection 190, the configuration parameter displaysection 182 is updated to display the data that is specific to theselected subsection 190. A section or subsection name 192 is displayedindicating the subsystem of the medical imaging scanner to which thedisplayed information pertains. Certain sections or subsections maynecessitate the display of multiple configuration parameters. As such,the configuration parameter display section 182 can be further brokeninto configuration groups 194. In this regard, a configuration groupname 196 is displayed. Within each configuration group 194 configurationparameter names 197 and corresponding configuration parameter values 198are displayed. Examples of configuration parameters include currentvalue, voltage value, table position, screen brightness, and the like.Configuration parameters can be represented in several formats such asstring, list of strings, number, list of numbers, floating-pointnumbers, matrix, and the like. Furthermore, the configuration parameterscan be displayed in various formats. For example, a string data type canbe displayed as a textbox, a part of a pull down list, a group ofselection buttons, and the like. Since the nature of this data isdynamic, the mechanism for generation of subsection name, group name,configuration parameter, as well as the specific means of displaying thevalues, are also dynamic.

Additionally, a user, after reviewing the configuration parameters inthe user interface 176, can update all or a portion of the values andthen submit the changes. The changes made can be of various types, suchas changing text in a textbox, selecting a different button in a group,selecting a different option in a pull down list, or checking adifferent checkbox in a list. In any case, the changes are implementedand configuration parameters are updated. Therefore, by gathering andorganizing the configuration parameters of a medical imaging scanner, auser can access the single, dynamic, user interface 176 containing thedata necessary to configure and maintain the medical imaging scanner.Furthermore, the user may edit the current configuration parameters ofthe medical imaging scanner within the single user interface 176 eitherlocally or remotely.

Also, a group of configuration parameters falling within a particularsubsection can be arranged in a number of fashions depending on the userinterface requirements. Should the user or designer desire to show allconfiguration parameters at once, without the need for scrolling withinthe window, the user can specify that the data be organized in aspecific number of rows and columns. On the other hand, if the user ordesigner desires a simpler display, the user can specify that the databe displayed in a single column. As previously shown with respect toFIG. 2, a layout table is used when generating the user interface thatmay contain any variation of rows and columns to organize the display asnecessary.

Similarly, as previously shown with respect to FIG. 3, there may bemultiple users that require varying levels of access to the informationdisplayed by the user interface. In this case, the user interfaceincludes profiles, whereby some users have the right to modify the datawhile other users may only review the data or part of the data.Specifically, an access control mechanism is included that shows theconfiguration parameter values as read-write, read-only, or hiddendepending upon the user profile of the user accessing the data.

Referring now to FIG. 5, an overview block diagram of a medicaldiagnostic and service networked system 210 is shown which includes aplurality of treatment stations or nodes, such as Station A 212, andStation B 214, which may include a medical treatment facility, hospital,clinic, or mobile imaging facility. The treatment stations 212, 214 maybe connected to a centralized facility 216 through a communicationslink, such as a network of interconnected server nodes. Each treatmentstation has operational software associated therewith which can beconfigured, serviced, maintained, upgraded, monitored, and enabled ordisabled locally at the station or from the centralized facility 216.

In general, a treatment site may have a number of devices such as avariety of medical diagnostic systems of various modalities. As anotherexample, in the present embodiment, the devices in a treatment station,such as that shown with reference to treatment station 212, may includea number of networked medical image scanners 218 connected to aninternal network 220 served by a single scanner 222 having a workstationconfigured to also act as a server, or configured as a stand-aloneserver without a medical image scanner associated therewith.Alternately, a treatment station or treatment site 214 can include anumber of non-networked medical image scanners 224, 226, and 228 eachhaving a computer or workstation associated therewith. Each scanner maybe of the same modality or be of different modality. Any imaging scannermodality is contemplated. In the case of treatment station 214, aninternal modem 230, 232, 234 may be included to connect the remotetreatment station to a communications link 236 to allow communicationbetween the treatment stations 212, 214 and a centralized facility 216.The communications link 236 is shown in phantom to indicate that it mayinclude an external public or semi-public communications network, suchas the internet, or may be a more secure dedicated communications linkor intranet.

The embodiment shown in FIG. 5 contemplates a medical facility havingsuch systems as MRI systems, ultrasound systems, x-ray systems, CTsystems, as well as PET systems, or any other type of medical imagingsystem, however, the present invention is not so limited to anyparticular imaging system. Such facilities may also provide services tocentralized medical diagnostic management systems, picture archiving andcommunications systems (PACS), teleradiology systems, etc.

As stated, these medical imaging systems regularly require setup,configuration, servicing, and maintenance. Service engineers and otherusers access configuration interfaces either through a workstationintegrated within the treatment station 212, 214 through a portableservice/configuration computer 238 that can be carried to the treatmentstation 212, 214, through a workstation 240 in a remote service station216 or through a mobile workstation 242 in a mobile service station 244when servicing the medical imaging scanner 218, 224, 226, 228. Theservice computer 238, 240, 242 is enabled to display the user interfaceof the present invention to enable the user to access and change systemconfiguration parameters of the medical imaging scanner 218, 224, 226,228 through an interface.

Through this architecture and technique it is possible to dynamicallygenerate a single interface for a medical imaging scanner to allow auser to review and edit configuration parameters of the medical imagingscanner from the single interface. The invention overcomes thelimitations present when requiring multiple review and edit interfaces.Furthermore, the technique facilitates remote servicing while providingspecific checks against erroneous configurations and unapproved access.

The invention described above is highly portable, highly customizable,and may be adapted to operate with a wide variety of medical imagingproducts regardless of modality. Specifically, because the invention isnot operating environment dependent, it may be integrated into multiplesystems regardless of operating system or hardware configuration. Theinvention provides a means of easily updating the web-based userinterface to display various visual representations and styles withinthe user interface. Furthermore, the current invention provides highlayout flexibility by placing the configuration parameters in a table.As such, the above described invention is highly flexible such that itmay be adapted to meet the needs and preferences of a wide variety ofsystems and users.

It is contemplated that the above architecture and technique can beembodied in any modality of medical imaging scanner or within a portableservicing device such that, when accessed by a user, the medical imagingscanner or portable servicing device is caused to implement the aboveprocess.

It is further contemplated that the above architecture and technique canbe embodied in a computer program, stored on a computer readable storagemedium, and executable by a local or remote computer. The program, whenexecuted by one or more processors of a computer system and/or server,causes the computer system and server to implement the above process.

The present invention has been described in terms of the preferredembodiments, and it is recognized that equivalents, alternatives, andmodifications, aside from those expressly stated, are possible andwithin the scope of the appending claims.

1-45. (canceled)
 46. A system for interfacing with a medical devicecomprising: a plurality of software components configured to: access andretrieve configuration profiles from a plurality of subsystems of amedical device; generate an interface showing a representation ofinformation contained in the configuration profiles of the subsystems ofthe medical device; and receive user alterations of the informationcontained in the configuration profiles communicated through theinterface.
 47. The system of claim 46 wherein the plurality of softwarecomponents is further configured to generate the interface showing therepresentation of the information contained in the configuration profileaccording to at least one of the information contained in theconfiguration profile and a user defined representation.
 48. The systemof claim 46 wherein the plurality of software components is furtherconfigured to receive a user profile and exclude information containedin the configuration profiles from display if the user profile is notdesignated for review of information contained in the configurationprofiles.
 49. The system of claim 46 wherein the plurality of softwarecomponents is further configured to receive a user profile and rejectuser alterations of the information contained in the configurationprofiles if the user profile is not designated for editing ofinformation contained in the configuration profiles.
 50. The system ofclaim 46 wherein the interface showing the representation of informationcontained in the configuration profiles is configured to be displayed ina single browser window.
 51. The system of claim 50 wherein the singlebrowser window is configured to display the information contained in theconfiguration profiles for review and receive user alterations of theinformation contained in the configuration profiles.
 52. The system ofclaim 51 wherein the plurality of software components is furtherconfigured to validate user alterations of the information contained inthe configuration profiles according to at least one of a configurationprofile name and a configuration profile type.
 53. A system fordynamically generating an interface comprising: an organizational datafile defining an organization of subsystems of a medical imaging device;at least one parsing component configured to extract configurationparameter names from the organizational data file and generate arepresentation of the organization of the subsystems of the medicalimaging device; and a configuration servlet to extract configurationparameters of the medical imaging device and associate the configurationparameters with the representation of the organization of the medicalimaging device and generate a display of the configuration parametersand representation of the organization of the subsystems of the medicalimaging device in a single user interface.
 54. The system of claim 53further comprising a layout information data file to map theconfiguration parameters to user defined layout preferences.
 55. Thesystem of claim 54 wherein the at least one parsing component is furtherconfigured to parse the layout information data file into rows andcolumns corresponding to the configuration parameters.
 56. The system ofclaim 54 wherein the configuration servlet is further configured togenerate the display of the representation of the organization of thesubsystems and configuration parameters according to the user definedlayout preferences.
 57. The system of claim 53 wherein the display ofthe configuration parameters enables review and editing of theconfiguration parameters in the single user interface.
 58. The system ofclaim 57 wherein the configuration servlet is configured to hidespecific configuration parameters if the current user is not permittedto view the specific configuration parameters.
 59. The system of claim53 wherein the organizational data file further includes data togenerate links to data that is external from the medical imaging device.60. The system of claim 53 further comprising an XML control fileincluding a map of each of a plurality of data types to a manner ofdisplaying each of the data types.
 61. The system of claim 53 furthercomprising a validation tool that includes a number of validationfunctions and is configured to dynamically validate user input into thesingle user interface and wherein the configuration servlet isconfigured to assign names to the number of validation functions. 62.The system of claim 61 wherein the user input into the single userinterface is validated based upon the validation function names.
 63. Amedical imaging device comprising: a plurality of subsystems configuredto execute at least one imaging application; and a computer programmedto: extract configuration parameters of the plurality of subsystems;generate an organizational representation of the plurality ofsubsystems; associate the configuration parameters with theorganizational representation of the plurality of subsystems; anddisplay the organizational representation of the plurality of subsystemsin a single user interface configured to receive user-definedalterations to the configuration parameters.
 64. The medical imagingdevice of claim 63 wherein the computer is further programmed tovalidate the user-defined alterations to the configuration parametersand if valid, implement the user-defined alterations.
 65. The medicalimaging device of claim 64 wherein the computer is further programmed tovalidate the user-defined alterations dynamically from at least one of aconfiguration parameter name and a configuration parameter type.